Scayn

Accounting and OCR app, 2025

Enhancing the existing app by implementing new functionalities for issuing proforma, advance, and final invoices

1. My role and the team

Role:
Business analyst

Team:
1 PM, 2 Backend Developers, 1 Frontend Developer, 1 Business Analyst (me 👋)

Contribution:
As the Business analyst, I played a role in preparing the development team during pre-sprint phases. My responsibilities focused on bridging gaps between business needs, user expectations, and technical requirements to ensure a smooth project kickoff. Specifically, I concentrated on:

🤝 Business needs: Identified gaps and ambiguities in the client-provided designs. I proactively engaged with stakeholders to resolve these issues early, ensuring developers had all the necessary information before starting their work.

🧑‍💻 End user needs: Conducted a thorough analysis of invoicing workflows (proforma, advance, and final invoices) to provide the development team with a comprehensive understanding of user processes.

⚖️ Additional requirements: Collected and documented legal and technical requirements to integrate the invoicing functionalities with Poland's national e-invoice system (KSeF).

2. Approach and deliverables

Functional gap analysis

  • I compared client designs against initial business requirements to ensure alignment,
  • I created detailed process flows highlighting missing steps (e.g., error handling, edge cases) and raised clarifying questions for stakeholders.

Approach

  • I developed a final process flow visualizing end-user workflows based on clarified requirements,
  • I supplemented design frames with insights gained from workshops and desk research (e.g., legal compliance).
Whiteboard with user flow followed by questions, answers, quotes and legal knowledge.

Legal and technical requirements documentation

  • I extracted key requirements from government technical documentation and legal guidelines for KSeF integration,
  • I generated sample XML files using AI tools and competition apps to demonstrate export functionality for developers,
  • Compiled all integration-related resources into a centralized repository with detailed instructions.
Part of team knowledge base in Figjam: notes, quotes, screenshots.

3. Impact

  • Streamlined development process by resolving design ambiguities upfront, reducing rework during sprints,
  • Enhanced developer efficiency by providing clear documentation, including sample XML files and integration guidelines,
  • Improved alignment between client expectations and technical implementation through proactive stakeholder communication,
  • Facilitated seamless compliance with legal requirements for KSeF integration, ensuring the product met regulatory standards.